SPE: document container type owner billing management - #11016

Category

• Content fix
• New article

Related issues

• None

What's in this Pull Request?

This PR documents standard-billing self-service for SharePoint Embedded container type owners and aligns billing-role guidance across the SharePoint Embedded documentation.

• Directs container type owners to the SharePoint Embedded Visual Studio Code extension or Model Context Protocol (MCP) server for standard-billing management.
• Documents Attach billing in the Visual Studio Code extension and the MCP server's billing_setup and billing_check tools as the supported owner facilities.
• Clarifies that non-administrator owners can manage standard billing only for container types they own.
• Clarifies that SharePoint Embedded Administrators and Global Administrators can manage any standard-billed container type in the developer tenant.
• Documents Billing Administrator or Global Administrator for consuming-tenant pass-through billing setup in the Microsoft 365 admin center.
• Clarifies that the SharePoint Embedded Administrator role alone doesn't grant access to that Microsoft 365 billing procedure.
• Preserves User org and user organization billing as names for the pass-through model.
• Links the Azure Owner and Contributor role definitions where those roles are required.
• Aligns developer, ISV, customer-setup, troubleshooting, and admin guidance across 12 existing articles.

The change intentionally doesn't add a dated What's new entry. Release timing remains separate from the documentation draft.

Validation

• SPE style, technical-accuracy, and implementation reviewers reviewed the original 12-article correction and the focused five-article review-feedback update.
• The SPE fix-suggester refined the billing-role draft. Focused implementation review and final style and accuracy repasses for the abstraction update returned no findings.
• A full DocFX build completed successfully with zero warnings or errors for the target articles. Existing unrelated repository warnings remain.
• git diff --check passes.
• Existing ms.date and other selected metadata values are unchanged from main.
• Relative Markdown links, heading anchors, VS Code and MCP workflow links, and Azure Owner and Contributor links were validated.
• The public content contains no raw billing resource payload, internal permission names, app IDs, rollout controls, internal links, or test-tenant details.